Conversation
…api-compat test failure Patched for python/pythoncapi-compat#169
|
It seems like you ran You should run |
|
What is the reason for using the custom script? |
runtests.py tries to test as many available Python versions as possible by testing these programs: PYTHONS = (
# CPython
"python3-debug",
"python3",
"python2.7",
"python3.6",
"python3.7",
"python3.8",
"python3.9",
"python3.10",
"python3.11",
"python3.12",
"python3.13",
"python3.13t",
"python3.14",
"python3.14t",
"python3.15",
"python3.15t",
# PyPy
"pypy",
"pypy2",
"pypy2.7",
"pypy3",
"pypy3.6",
"pypy3.7",
"pypy3.8",
"pypy3.9",
"pypy3.10",
"pypy3.11",
)pytest only runs tests on a single Python version. |
|
Is there a tradeoff to using the relative import here? For context, I maintain the srctools package in nixpkgs & testing for python packages is handled by pytest. In this case, the test is run for each build of the package (currently Python 3.13 & 3.14), as those are the versions of Python available in nixpkgs We would have to use the |
|
I don't see the need for this change. As Victor points out, the docs show how to run the tests. Suggesting to close this. |
Could you please explain what the drawback to using a relative import here is? I don't understand |
Fix for the following test error:
Not sure why this is only an issue now, however this seems to be the correct approach